Claude finished @hassandotcms's task in 1m 24s —— View job

Rollback Safety Analysis

• Read rollback-unsafe categories reference
• Get full PR diff
• Analyze diff against all unsafe categories
• Apply label

Result: ✅ Safe To Rollback

Scope of changes:

Analysis against every unsafe category:

Reasoning: parseBlockEditor is a private method deep inside the AI embeddings pipeline. Its output feeds into the vector store as embedding source text — format changes here affect only the quality of future embeddings for Story Block fields; they do not alter any database schema, Elasticsearch mapping, stored data contract, or API surface. Rolling back to N-1 reverts to the Tika path; any Markdown-format embeddings already written are semantically compatible (cosine similarity still works), and no data is lost.

🤖 dotBot Review (Bedrock)

Reviewed 3 file(s); 1 candidate(s) → 1 confirmed, 0 uncertain (unverified, kept for review).

Confirmed findings

• 🟡 Medium dotcms-integration/src/test/java/com/dotcms/ai/util/ContentToStringUtilTest.java:100 — Missing test coverage for empty/null Story Block field handling
  The test testParseBlockEditorWithTableAndCodeBlock validates correct Markdown conversion of valid Story Block JSON but lacks cases for empty/null inputs. While parseBlockEditor uses @NotNull, callers might still pass empty strings (e.g., from empty content fields). The test sets body to STORY_BLOCK_WITH_TABLE_AND_CODE (line 97) but never tests empty body values. Without tests for empty/invalid JSON inputs, potential issues in StoryBlockMap constructor (e.g., NPEs, JSON parsing errors) or empty return values remain unverified.

_{us.deepseek.r1-v1:0 · Run: #28451883674 · tokens: in: 14379 · out: 3070 · total: 17449 · calls: 6 · est. ~$0.036}